Efficient realization of coverage collection in emulation

ABSTRACT

Coverage event counters for hardware verification emulations are implemented as linear feedback shift register-based counters generating encoded counter values indicative of a detected number of coverage events. To decode those counter values, a counter algorithm utilized to generate the encoded counter value may continue to be iterated after counting is complete until reaching a defined pattern, while counting the number of iterations (K) necessary to reach the defined pattern. The resulting counter value having the defined pattern is correlated with a mapping table to identify a numerical value, and an ordinal counter value indicative of the number of coverage events is determined based on the identified numerical value, less K.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority from U.S. Provisional Appl. Ser. No. 62/594,297, filed Dec. 4, 2017, which is incorporated herein by reference in its entirety.

COPYRIGHT NOTICE

The assignee of this patent document has no objection to the facsimile reproduction by anyone of the patent document itself, or of the patent application, as it appears in the files of the United States Patent and Trademark Office, but otherwise reserves all rights whatsoever in any included works of authorship protected by copyright.

SPECIFICATION—DISCLAIMER

In the following Background, Summary, and Detailed Description, headings should not be construed as necessarily limiting. In the following Background, Summary and Detailed Description, the citation or identification of any publication does not signify relevance or status as prior art for any of the claimed or described embodiments. Paragraphs for which the text is all italicized signifies text that is common to multiple Synopsys patent specifications.

BACKGROUND

Coverage data collection is an important means for hardware verification. There are many kinds of coverage data that may be collected on verification test runs: functional coverage data, code coverage data, toggle coverage data, etc. For many kinds of coverage data collection, a coverage event (e.g., bit toggle, occurrence of some temporal sequence, simultaneous assertion of two specific signals, etc.) has associated a counter containing a number of times this coverage event has been hit during the test run.

In emulation, for each coverage event usually a separate counter is allocated. Since the coverage space size may be huge, many millions of hit counters may need to be allocated in the emulator hardware. The contents of these counters should then be transmitted to the host computer. Both coverage counter allocation and communication with the host impose a heavy burden on an emulator and result in a significant requirement for capacity and performance overhead. There is also a tradeoff between capacity and communication overhead introduced by the coverage collection. In addition to performance and capacity overhead, the communication between the emulator and the host requires complex FPGA routing to allow connection of every counter with the host. This makes FPGA compilation much more complex and leads to less efficient use of FPGA resources, thus increasing even more the capacity overhead, let alone of increasing the model compilation time.

It has been determined to allocate all counters on the host. This requires sending signal traces to the host, with subsequent simulation of the stimuli collected in these traces using simulation software in the postprocessing mode. The downside of this solution is the overhead introduced by the signal trace collection, communication with the host, sophisticated routing and slow simulation performance.

Various embodiments as discussed herein address the resource overhead problem introduced by coverage collection support in emulation: to minimize capacity, communication and routing overhead.

SUMMARY

The claims signify a brief description of one or more of the innovations, embodiments, and/or examples found within this disclosure.

Example features and benefits of various embodiments as discussed herein are:

-   -   Using linear feedback shift registers (LFSR) for compact         coverage hit counter implementation. This implementation         introduces much lower capacity overhead than the conventional         counter implementation.     -   Efficient counter decoding algorithm able to quickly decode         millions of counters at the end of emulation or at any other         specific moment if required.     -   Reading counter contents using FPGA scan chains to avoid routing         and communication overhead required to pass counter values from         emulator to the host computer.

Certain embodiments are directed to a coverage event counter for hardware verification. In certain embodiments, the coverage event counter comprises: an n-bit linear feedback shift register (LFSR) for incrementing a counter upon detection of a coverage event; a decoder for correlating a bit pattern of the counter with numeric values, wherein the counter decoder is configured to: iterate the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value; correlate the (n−m) bit reduced value against one or more mapping tables to identify a numerical value; and decode the bit pattern counter based on the numerical value and the value K to generate a numerical counter value. The number of iterations of the counter K is counted, and is dependent on the counter value. The number of iterations of K is determined based on the number of iterations necessary to reach a counter value having a defined pattern.

In various embodiments, a mapping table of the one or more mapping tables is a static mapping table containing 2^(n−m)−1 values. Moreover, the one or more mapping tables may be each implemented as a hashed container. In certain embodiments, the consistent m-bit pattern portion is an m-bit string of binary zeros. In various embodiments, the LFSR is a right-shift register, and wherein the m-bit string of binary zeros comprises the m most significant bits of the n-bit counter. Moreover, decoding the bit pattern counter may comprise subtracting K from the numerical value to generate the numerical counter value. The decoder may be further configured to: detect an overflow condition based on the bit pattern of the counter; set the numerical counter as a base numerical counter value; and loop through processes for: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value for an overflow portion; correlating the (n−m) bit reduced value for the overflow portion against one or more mapping tables to identify a numerical value; decoding the overflow portion of the bit pattern counter based on the numerical value and the value K to generate a numerical counter value for the overflow portion; and adding the numerical counter value for the overflow portion with the base numerical counter value to generate a complete numerical counter value.

In certain embodiments, the coverage event counter further comprises a scan chain to send the numerical counter value to a host computer. In certain embodiments, the coverage event counter is executable as a portion of a hardware verification emulator. Moreover, the decoder may be embodied as a module which may be implemented in hardware or software. In certain embodiments, the decoder may be a module implemented as a plurality of logic gates. In other embodiments, the decoder may be module implemented in software executed on a processor. In certain embodiments, the one or more mapping tables comprises a plurality of mapping tables, wherein each of the plurality of mapping tables correlates to a different ordinal value range. Moreover, the LFSR may comprise a shift register, a flip flop, and an XOR gate. In certain embodiments, the n-bit LFSR is a 31-bit LFSR or a 63-bit LFSR, and K may be equal to 8.

Various embodiments are directed to a method for counting coverage events for hardware verification. In certain embodiments, the method comprises: incrementing an n-bit counter of a linear feedback shift register (LFSR) for each detected coverage event; correlating a bit pattern of the counter with numeric values by: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value; correlating the (n-m) bit reduced value against one or more mapping tables to identify a numerical value; and decoding the bit pattern counter based on the numerical value and the value K to generate a numerical counter value.

In various embodiments, one of the one or more mapping tables is a static mapping table containing 2^(n−m)−1 values. In certain embodiments, the one or more mapping tables are each implemented as a hashed container. In other embodiments, the one or more mapping tables are each implemented as a sorted array, which may be usable with a binary search. Moreover, the consistent m-bit pattern portion may be an m-bit string of binary zeros. In certain embodiments, the LFSR is a left-shift register, and wherein the m-bit string of binary zeros comprises the m most significant bits of the n-bit counter. In various embodiments, decoding the bit pattern counter comprises subtracting K from the numerical value to generate the numerical counter value. Moreover, the decoder may be further configured to: detect an overflow condition based on the bit pattern of the counter; set the numerical counter as a base numerical counter value; and loop through processes for: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value for an overflow portion; correlating the (n−m) bit reduced value for the overflow portion against one or more mapping tables to identify a numerical value; decoding the overflow portion of the bit pattern counter based on the numerical value and the value K to generate a numerical counter value for the overflow portion; and estimating a complete numerical counter value of greater than K added with the numerical value identified from the one or more mapping tables. In various embodiments, the method further comprises sending the numerical counter value to a host computer via a scan chain. In certain embodiments, the one or more mapping tables comprise a plurality of mapping tables, wherein each of the plurality of mapping tables correlates to a different ordinal value range. Moreover, The LFSR may comprise a shift register, a flip flop, and an XOR gate. In certain embodiments, the n-bit LFSR is a 31-bit LFSR or a 63-bit LFSR, and m may be equal to 8.

This Summary does not attempt to completely signify any particular innovation, embodiment, or example as it can be used in commerce. Additionally, this Summary is not intended to signify essential elements of an innovation, embodiment or example or to limit the scope of the subject matter of this disclosure.

The innovations, embodiments, and/or examples found within this disclosure are not all-inclusive, but rather describe the basic significance of the subject matter. Accordingly, one use of this Summary is as a prelude to a Detailed Description presented later.

DRAWINGS

The following Detailed Description, Figures, and appended Claims signify the nature and advantages of the innovations, embodiments and/or examples of the claimed inventions. All of the Figures signify innovations, embodiments, and/or examples of the claimed inventions for purposes of illustration only and do not limit the scope of the claimed inventions. Such Figures are not necessarily drawn to scale, and are part of the Disclosure.

In the Figures, similar components or features may have the same, or similar, reference signs in the form of labels (such as alphanumeric symbols, e.g., reference numerals), and may signify similar or equivalent functionality. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label. A brief description of the Figures is below.

Various figures are incorporated herein. In such various figures, reference signs may be omitted as is consistent with accepted engineering practice; however, one of ordinary skill in the art will understand that the illustrated components are readily understood when viewed in context of the illustration as a whole and the accompanying disclosure describing such various figures.

FIG. 1 is a flowchart illustrating various operations in the design and fabrication of an integrated circuit in accordance with an embodiment of the present disclosure.

FIGS. 2A, 2B and 2C are simplified block diagrams of a computer system suitable for use with embodiments of the technology, as well as circuit design and circuit embodiments of the technology. In such various figures, reference signs may be omitted as is consistent with accepted engineering practice; however, one of ordinary skill in the art will understand that the illustrated components are readily understood when viewed in context of the illustration as a whole and the accompanying disclosure describing such various figures.

FIG. 3 depicts a block diagram of an emulation system.

FIGS. 4-5 are example block diagrams of counters according to various embodiments.

DETAILED DESCRIPTION

The Figures and the following Detailed Description signify innovations, embodiments and/or examples by way of illustration only, with various features, structures or characteristics described together in a single embodiment to streamline the disclosure. Variations of any of the elements, processes, machines, systems, manufactures or compositions disclosed by such exemplary innovations, embodiments and/or examples will be readily recognized and may be used in commerce without departing from the principles of what is claimed. The Figures and Detailed Description may also signify, implicitly or explicitly, advantages and improvements of a subset of the exemplary embodiments described herein.

In the Figures and Detailed Description, numerous specific details may be described to enable one or more of the exemplary innovations, embodiments and/or examples. In the interest of not obscuring the presentation of the exemplary innovations, embodiments and/or examples in the following Detailed Description, some processing steps or operations that are known in the art may be combined together for presentation and for illustration purposes and might not be described in detail. However, a person skilled in the art will recognize that these exemplary innovations, embodiments and/or examples may be used in commerce without these specific details or with equivalents thereof. In other instances, well-known processes and devices are not described in detail as not to unnecessarily obscure aspects of these exemplary innovations, embodiments and/or examples. In other instances, some processing steps or operations that are known in the art may not be described at all. The following description is instead focused on the distinctive features or elements of various exemplary innovations, embodiments and/or examples. Furthermore, while this description may refer to some components of the structure in the singular tense, more than one component may be depicted throughout the Figures and like components are labeled with like numerals.

Detailed Description Technology Support—General Computer Explanation

FIGS. 2A, 2B and 2C are simplified block diagrams of a computer system suitable for use with embodiments of the technology, as well as circuit design and circuit embodiments of the technology.

In FIG. 2A, computer system 3110 typically includes at least one computer or processor 3114 which communicates with a number of peripheral devices via bus subsystem 3112. Typically, the computer can include, or the processor can be, any of a microprocessor, graphics processing unit, or digital signal processor, and their electronic processing equivalents, such as an Application Specific Integrated Circuit (ASIC) or Field Programmable Gate Array (FPGA). The terms ‘processor’ and ‘computer’ are further defined below. These peripheral devices may include a storage subsystem 3124, comprising a memory subsystem 3126 and a file storage subsystem 3128, user interface input devices 3122, user interface output devices 3120, and a network interface subsystem 3116. The input and output devices allow user interaction with computer system 3110.

The computer system may be a server computer, a client computer, a workstation, a mainframe, a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a smartphone, a web appliance, a rack-mounted “blade”, a kiosk, a television, a game station, a network router, switch or bridge, or any data processing machine capable of executing instructions 124 (sequential or otherwise) that specify actions to be taken by that machine.

The computer system typically includes an operating system, such as Microsoft's Windows, Sun Microsystems's Solaris, Apple Computer's Mac OS, Linux or Unix. The computer system also typically can include a Basic Input/Output System (BIOS) and processor firmware. The operating system, BIOS and firmware are used by the processor to control subsystems and interfaces connected to the processor. Typical processors compatible with these operating systems include the Pentium and Itanium from Intel, the Opteron and Athlon from Advanced Micro Devices, and the ARM processor from ARM Holdings.

Innovations, embodiments and/or examples of the claimed inventions are neither limited to conventional computer applications nor the programmable apparatus that run them. For example, the innovations, embodiments and/or examples of what is claimed can include an optical computer, quantum computer, analog computer, or the like. The computer system may be a multi-processor or multi-core system and may use or be implemented in a distributed or remote system. The term ‘processor’ here is used in the broadest sense to include a singular processor and multi-core or multi-processor arrays, including graphic processing units, digital signal processors, digital processors and combinations of these devices. Further, while only a single computer system or a single machine may be illustrated, the use of a singular form of such terms shall also signify any collection of computer systems or machines that individually or jointly execute instructions 124 to perform any one or more of the sets of instructions discussed herein. Due to the ever-changing nature of computers and networks, the description of computer system 3110 depicted in FIG. 2A is intended only as one example for purposes of illustrating the preferred embodiments. Many other configurations of computer system 3110 are possible having more or less components than the computer system depicted in FIG. 2A.

Network interface subsystem 3116 provides an interface to outside networks, including an interface to communication network 3118, and is coupled via communication network 3118 to corresponding interface devices in other computer systems or machines. Communication network 3118 may comprise many interconnected computer systems, machines and communication links. These communication links may be wireline links, optical links, wireless links, or any other devices for communication of information. Communication network 3118 can be any suitable computer network, for example a wide area network such as the Internet, and/or a local area network such as Ethernet. The communication network can be wired and/or wireless, and the communication network can use encryption and decryption methods, such as is available with a virtual private network.

The communication network uses one or more communications interfaces, which can receive data from, and transmit data to, other systems. Embodiments of communications interfaces typically include an Ethernet card, a modem (e.g., telephone, satellite, cable, or ISDN), (asynchronous) digital subscriber line (DSL) unit, Firewire interface, USB interface, and the like. One or more communications protocols can be used, such as HTTP, TCP/IP, RTP/RTSP, IPX and/or UDP.

User interface input devices 3122 may include an alphanumeric keyboard, a keypad, pointing devices such as a mouse, trackball, touchpad, stylus, or graphics tablet, a scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, or microphones, eye-gaze recognition, brainwave pattern recognition, and other types of input devices. Such devices can be connected by wire or wirelessly to a computer system. In general, use of the term “input device” is intended to include all possible types of devices and ways to input information into computer system 3110 or onto communication network 3118. User interface input devices typically allow a user to select objects, icons, text and the like that appear on some types of user interface output devices, for example, a display subsystem.

User interface output devices 3120 may include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display subsystem may include a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), a projection device, or some other device for creating a visible image such as a virtual reality system. The display subsystem may also provide non-visual display such as via audio output or tactile output (e.g., vibrations) devices. In general, use of the term “output device” is intended to include all possible types of devices and ways to output information from computer system 3110 to the user or to another machine or computer system.

Memory subsystem 3126 typically includes a number of memories including a main random-access memory (RAM) 3130 (or other volatile storage device) for storage of instructions and data during program execution and a read only memory (ROM) 3132 in which fixed instructions are stored. File storage subsystem 3128 provides persistent storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, a flash memory, or removable media cartridges. The databases and modules implementing the functionality of certain embodiments may be stored by file storage subsystem 3128.

Bus subsystem 3112 provides a device for letting the various components and subsystems of computer system 3110 communicate with each other as intended. Although bus subsystem 3112 is shown schematically as a single bus, alternative embodiments of the bus subsystem may use multiple busses. For example, RAM-based main memory can communicate directly with file storage systems using Direct Memory Access (DMA) systems.

FIG. 2B shows a memory 3140 such as a non-transitory, computer readable data and information storage medium associated with file storage subsystem 3128, and/or with network interface subsystem 3116, and can include a data structure specifying a circuit design. The memory 3140 can be a hard disk, a floppy disk, a CD-ROM, an optical medium, removable media cartridge, or other medium that stores computer readable data in a volatile or non-volatile form. Software read into a computer from such a memory can be converted at a selected instance in time from a tangible form to a transmission signal that is propagated through a medium (such as a network, connector, wire, or trace as an electrical pulse or a medium such as space or an atmosphere as electromagnetic radiation with wavelengths in the electromagnetic spectrum longer than infrared light).

FIG. 2C signifies an integrated circuit 3190 created with the described technology that includes one or more cells selected, for example, from a cell library.

Detailed Description Technology Support—Hardware/Software Equivalence

Some of the innovations, embodiments and/or examples described herein comprise and/or use a processor. As used herein, the term ‘processor’ signifies a tangible data and information processing device that physically transforms data and information, typically using a sequence transformations (also referred to as ‘operations’). Data and information can be physically represented by an electrical, magnetic, optical or acoustical signal that is capable of being stored, accessed, transferred, combined, compared, or otherwise manipulated by the processor. The term “processor” can signify a singular processor and multi-core systems or multi-processor arrays, including graphic processing units, digital signal processors, digital processors or combinations of these elements.

The processor can be electronic, for example, comprising digital logic circuitry (for example, binary logic), or analog (for example, an operational amplifier). The processor can also be non-electronic, for example, as seen in processors based on optical signal processing, DNA transformations or quantum mechanics, or a combination of technologies, such as an optoelectronic processor. For data and information structured in binary form, any processor that can transform the data and information using the AND, OR and NOT logical operations (and their derivatives, such as the NAND, NOR, and XOR operations) can transform the data and information using any function of Boolean logic. A processor such as an analog neural network processor can also transform data and information non-digitally. There is no scientific evidence that any of these processors are processing, storing and retrieving data and information, in any manner or form equivalent to the bioelectric structure of the human brain.

The one or more processors may also operate to support performance of the relevant operations in a ‘cloud computing’ environment or as a ‘software as a service’ (SaaS). For example, at least some of the operations may be performed by a group of processors available at a distributed or remote system, these processors accessible via a communications network (e.g., the Internet) and via one or more software interfaces (e.g., an application program interface (API).)

As used herein, the term ‘module’ signifies a tangible data and information processing device that typically is limited in size and/or complexity. For example, the term ‘module’ can signify one or more methods or procedures that can transform data and information. The term ‘module’ can also signify a combination of one or more methods and procedures in a computer program. The term ‘module’ can also signify a small network of digital logic devices, in which interconnections of the logic devices give structure to the network. Methods and procedures comprising a module, specified in a specialized language, such as System C, can be used to generate a specification for a network of digital logic devices that process data and information with exactly the same results as are obtained from the methods and procedures.

A module can be permanently configured (e.g., hardwired to form hardware), temporarily configured (e.g., programmed with software), or a combination of the two configurations (for example, a structured ASIC). Permanently configured modules can be manufactured, for example, using Application Specific Integrated Circuits (ASICs) such as Arithmetic Logic Units (ALUs), Programmable Logic Arrays (PLAs), or Read Only Memories (ROMs), all of which are typically configured during manufacturing. Temporarily configured modules can be manufactured, for example, using Field Programmable Gate Arrays (FPGAs—for example, sold by Xilink or Intel's Altera), Random Access Memories (RAMs) or microprocessors. A module is configured to process data and information, typically using a sequence transformations (also referred to as ‘operations’) applied to the data and information (or in the case of ROMs and RAMS, transforming data and information by using the input information as an address for memory that stores output data and information), to perform aspects of the present innovations, embodiments and/or examples of the invention.

Modules that are temporarily configured need not be configured at any one instance in time. For example, a processor comprising one or more modules can have the modules configured at different times. The processor can comprise a set of one or more modules at one instance of time, and to comprise a different set of one or modules at a different instance of time. The decision to manufacture or implement a module in a permanently configured form, a temporarily configured form, or a combination of the two forms, may be driven by cost, time considerations, engineering constraints and/or specific design goals. The “substance” of a module's processing is independent of the form in which it is manufactured or implemented.

As used herein, the term ‘algorithm’ signifies a process comprising a sequence or set of operations or instructions that a module can use to transform data and information to achieve a result. A module can comprise one or more algorithms. As used herein, the term ‘thread’ refers to a sequence of instructions that can comprise a subset of the instructions of an entire process or algorithm. A process or algorithm can be partitioned into multiple threads that can be executed in parallel.

As used herein, the term ‘computer’ includes at least one information processor that, for example, can perform certain operations such as (but not limited to) the AND, OR and NOT logical operations using electronic gates that can comprise transistors, with the addition of memory (for example, memory based on flip-flops using the NOT-AND or NOT-OR operation). Such a processor is said to be Turing-complete or computationally universal. A computer, whether or not it is a digital computer, typically comprises many modules.

As used herein, the term ‘software’ or ‘program’ signifies one or more algorithms and data structures that configure a processor for use in the innovations, embodiments and examples described in this specification. Such devices configurable by software include one or more computers, for example, standalone, client or server computers, or one or more hardware modules, or systems of one or more such computers or modules. As used herein, the term “software application” signifies a set of data and instructions that configure the processor to achieve a specific result, for example, to perform word processing operations, or to encrypt a set of data.

As used herein, the term ‘programming language’ signifies a grammar and syntax for specifying sets of instruction and data that comprise software. Programming languages include assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more higher level languages, such as conventional procedural programming languages, for example, the “C” programming language or similar programming languages (such as SystemC), or object oriented programming language such as Smalltalk, C++ or the like, and any future equivalent programming languages.

Software is entered into, equivalently, read into, one or memories of the computer or computer system from a data and information storage device. The computer typically has a device for reading storage media that is used to transport the software, or has an interface device that receives the software over a network. This process is discussed in the General Computer Explanation section.

Detailed Description Technology Support—EDA System/Workflow Explanation

FIG. 1 illustrates various processes performed in the design, verification, and fabrication of an item of manufacture such as an integrated circuit using software tools with a computer, and possibly special hardware-assisted tools, to transform and verify design data and instructions that represent the integrated circuit. These processes start with the generation of a product idea (110) with information supplied by a designer, information which is transformed during a process to create an item of manufacture (referred to herein as a design or device) that uses EDA software tools (112), which may also be signified herein as EDA software, as a design tool or a verification tool. When the design is finalized, it can be taped-out (134), which typically is when artwork (e.g., geometric patterns) for the integrated circuit is sent to a fabrication facility to manufacture the mask set, which is then used to manufacture the integrated circuit. After tape-out, a semiconductor die is fabricated (136) and packaging and assembly processes (138) are performed, which result in the finished integrated circuit (140) which may also be signified herein as a circuit, device, component, chip or SoC (System on Chip).

Items of manufacture, for example, a circuit or system are used in commerce at a variety of levels of abstraction ranging from low-level transistor layouts to high-level description languages. Most designers start at high-level of abstraction to design their circuits and systems, using a hardware description language (HDL) such as VHDL, Verilog, SystemVerilog, SystemC, MyHDL or OpenVera. The high-level HDL is easier for developers to comprehend, especially for a vast system, and may describe highly complex concepts that are difficult to grasp using a lower level of abstraction. The HDL description may be converted into other levels of abstraction as is helpful to the developers. For example, a high-level description may be converted to a logic-level register transfer level (RTL) description, a gate-level (GL) description, a layout-level description, or a mask-level description. Each lower abstraction level introduces more detail into the design description. The lower-levels of abstraction may be generated automatically by computer, derived from a design library, or created by another design automation technique. An example of a specification language at a lower level of abstraction is SPICE, much used detailed descriptions of analog-based circuits.

A design process that uses EDA software tools (112) includes processes 114-132, which are described below. This design flow description is for illustration purposes only and is not meant to limit the present disclosure. For example, an actual integrated circuit design may require a designer to perform the design operations in a different sequence than the sequence described herein.

During system design (114), a designer describes the functionality to be manufactured. The designer can also perform what-if planning to refine the functionality and to check costs, etc. Hardware-software architecture partitioning can occur at this stage. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Model Architect, Saber, System Studio, and Designware products.

During logic design and functional verification (116), modules in the circuit are specified in one or more hardware description languages, or HDLs, and the design in HDL is checked for functional accuracy, that is, to match the requirements of the specification of the circuit or system being designed to ensure that the design produces the correct outputs. Exemplary HDL languages are Verilog, VHDL and SystemC. Functional verification is typically done by using software-based simulators and other tools such as testbench generators, static HDL checking tools and formal verification tools. In some situations, special hardware referred to as ‘emulators’ or ‘prototyping systems’ are used to speed up the functional verification. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: VCS, Vera, Designware, Magellan, Formality, ESP and Leda products. Exemplary emulator and prototyping products also available from Synopsys that can be used at this state include: Zebu® and Protolink® (®=“Registered Trademark”).

During synthesis and design for test (118), HDL code is translated to a netlist. This netlist can be optimized for the target technology. Additionally, tests can be designed and implemented to check the finished integrated circuit. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Design Compiler, Physical Compiler, Test Compiler, Power Compiler, FPGA Compiler, Tetramax, and Designware products.

During netlist verification (120), the netlist is checked for compliance with timing constraints and for correspondence with the HDL code. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Formality, Primetime, and VCS products.

During design planning (122), an overall floor plan for the integrated circuit is constructed and analyzed for timing and top-level routing. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Astro and IC Compiler products.

During layout implementation (124), the physical placement (positioning of circuit elements such as transistors or capacitors) and routing (connection of the same by a plurality of conductors) occurs, as can selection of library cells to perform specific logic functions. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: the Astro and IC Compiler products.

During analysis and extraction (126), the circuit function is verified at the layout level, which permits refinement of the layout design. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Astrorail, Primerail, Primetime, and Star RC/XT products.

During physical verification (128), the layout design is checked to ensure correctness for manufacturing constraints such as DRC constraints, electrical constraints, lithographic constraints, and circuitry function matching the HDL design specification. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include the Hercules product.

During resolution enhancement (130), geometric manipulations of the layout are performed to improve manufacturability of the design. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include: Proteus products.

During tape-out, data is created to be used (after lithographic enhancements are applied if appropriate) for production of lithography masks. Example EDA software products from Synopsys, Inc., that can be used during tape-out include the IC Compiler and Custom Designer families of products.

During mask-data preparation (132), the tape-out data is used to produce lithography masks that are used to produce finished integrated circuits. Exemplary EDA software products from Synopsys, Inc. of Mountain View, Calif. that can be used at this stage include the CATS family of products.

For all of the above mentioned integrated circuit design tools, similar tools from other EDA vendors, such as Cadence, Siemens, other corporate entities or various non-commercial tools from universities, or open source repositories, can be used as an alternative.

Embodiments of the present disclosure can be used during one or more of the above-described stages. Specifically, some embodiments of the present disclosure can be used in EDA software (112).

A storage subsystem is preferably used to store the programs and data structures that provide the functionality of some or all of the EDA tools described herein, and tools applied for development of cells for the library and for physical and logical design using the library. These programs and data structures are generally executed by one or more processors in a manner known to those of ordinary skill in the art.

Detailed Description—Technology Support Emulation Environment Explanation

An EDA software system, such as element 3012 depicted in FIG. 1, typically includes an emulation system 3054 to verify the functionality of the circuit design. FIG. 3 depicts a typical emulation system which includes a host computer system 3300 (often part of an EDA system) and an emulator system 3202 (typically a set of programmable devices such as Field Programmable Gate Arrays (FPGAs)). The host system generates data and information, typically using a compiler 3210, to configure the emulator to emulate a circuit design. One of more circuit designs to be emulated are referred to as a DUT (Design Under Test). The emulator is a hardware system that emulates a DUT, for example, to use the emulation results for verifying the functionality of the DUT. One example of an emulation system that can be used for the embodiments disclosed herein is the ZeBu Server available from Synopsys, Inc.

The host system 3300 comprises one or more processors. In the embodiment where the host system is comprised of multiple processors, the functions described herein as being performed by the host system may be distributed among the multiple processors.

The host system 3300 typically includes a compiler 3210 that processes code written in a hardware description language that represents a DUT, producing data (typically binary) and information that is used to configure the emulation system 3202 to emulate the DUT. The compiler 3210 may transform, change, reconfigure, add new functions to, and/or control the timing of the DUT.

The host system and emulator exchange data and information using signals carried by an emulation connection. The connection can be one or more electrical cables, for example, cables with pin configurations compatible with the RS232 or USB protocols. The connection can be a wired communication medium or network, such as a local area network, or a wide area network such as the Internet. The connection can be a wireless communication medium or a network with one or more points of access, using a wireless protocol such as Bluetooth® or IEEE 802.11. The host system and emulator can exchange data and information through a third device, such as a network server.

The emulator includes multiple FPGAs (or other programmable devices), for example, elements 32041 to 304N in FIG. 3. Each FPGA can include one or more FPGA interfaces through which the FPGA is connected to other FPGAs of the emulator (and potentially other emulator hardware components), in order for the FPGAs to exchange signals. An FPGA interface may also be referred to as an input/output pin or an FPGA pad. While some embodiments disclosed herein make use of emulators comprising FPGAs, other embodiments can include other types of logic blocks instead of, or along with, the FPGAs for emulating DUTs, for example, custom FPGAs, specialized ASICs for emulation or prototyping, memories, and input/output devices.

A programmable device may include an array of programmable logic blocks and a hierarchy of reconfigurable interconnects that allow the programmable logic blocks to be connected to each other according to the descriptions in the HDL code. Each of the programmable logic blocks can be configured to perform complex combinational functions, or merely simple logic gates, such as AND, and XOR logic blocks.

In many FPGAs, logic blocks also include memory elements, which may be simple latches, flip-flops or more complex blocks of memory. Depending on the length of the interconnections between different logic blocks, signals may arrive at input terminals of the logic blocks at different times.

Programmable processors 32041-3204N may be placed into one or more hardware boards 32121 through 3212M. Many of such boards may be placed into a hardware unit, e.g. 32141. The boards within a unit may be connected using the backplane of the unit or any other types of connections. In addition, multiple hardware units (e.g., 32141 through 3214K) may be connected to each other by cables or any other means to form a multi-unit system. In general, the hardware emulation or prototype system 3202 may be formed using a single board, a single unit with multiple boards, or with multiple units without departing from the teachings of the present disclosure.

For a DUT that is to be emulated, the emulator receives from the host system one or more bit files including a description of the DUT. The bit files further specify partitions of the DUT created by the host system with trace and injection logic, mappings of the partitions to the FPGAs of the emulator, and design constraints. Based on the bit files, the emulator configures the FPGAs to perform the functions of the DUT. With some emulators, one or more FPGAs of an emulator already have the trace and injection logic built into the silicon of the FPGA. For this type of emulator, the FPGAs don't have to be configured by the host system to emulate trace and injection logic.

The host system 3110 receives (e.g., from a user) a description of a DUT that is to be emulated. In one embodiment, the DUT description is in a hardware description language (HDL), such as register transfer language (RTL). In another embodiment, the DUT description is in netlist level files, or a mix of netlist level files and HDL files. If part of the DUT description or the entire DUT description is in a HDL, the host system synthesizes the DUT description to create a gate level netlist based on the DUT description. A host system can use the netlist of the DUT to partition the DUT into multiple partitions, with some of these partitions including trace and injection logic. The trace and injection logic traces interface signals exchanged via the interfaces of an FPGA. Additionally, the trace and injection logic can be used to inject traced interface signals into the logic of the FPGA. The host system maps each partition to an FPGA of the emulator. With some emulators, the trace and injection logic is only included in select partitions for a group of FPGAs. The trace and injection logic can be built into one or more of the FPGAs of an emulator. The host system can synthesize multiplexers to be mapped into the FPGAs. The multiplexers can be used by the trace and injection logic to inject interface signals into the DUT logic.

The host system creates bit files describing each partition of the DUT and the mapping of the partitions to the FPGAs. For partitions in which trace and injection logic was incorporated, the bit files also describe the incorporation of the logic. The bit files may also include place and route information and design constraints. The host system stores the bit files and also stores for components of the DUT information describing which FPGAs are to emulate each component of the DUT (to which FPGAs each component is mapped).

Upon request, the host system transmits the bit files to the emulator. The host system instructs the emulator to emulate the DUT. During emulation of the DUT or at the end of the emulation, the host system receives emulation results from the emulator through the emulation connection. Emulation results are data and information generated by the emulator based on the emulation of the DUT. The emulation results include interface signals (states of interface signals) traced by the trace and injection logic of each FPGA. The host system can stores the emulation results, or transmit them to another processing system.

After emulation of the DUT, a user may request to debug a component of the DUT. If such a request is made the user may provide a time period of the emulation to debug. The host system identifies which FPGAs are configured to emulate the component based on the stored information. The host system retrieves stored interface signals associated with the time period and traced by the trace and injection logic of each identified FPGA. The host system instructs the emulator to re-emulate the identified FPGAs, either one by one, multiple at a time, or altogether. The host system transmits the retrieved interface signals to the emulator in order to re-emulate the component for the time period. The trace and injection logic of each identified FPGA injects its respective interface signals received from the host system into the logic of the DUT mapped to the FPGA. In case of multiple re-emulations of an FPGA, the results may be merged all together to have a full debug view.

The host system receives from the emulator signals traced by logic of the identified FPGAs during the re-emulation of the component. The host system stores the signals received from the emulator. The signals traced during the re-emulation can have a higher sampling rate than during the initial emulation. For example, in the initial run a traced signal may be comprised of a saved hardware state every X milliseconds. However, in the re-emulation the traced signal may be comprised of a saved hardware state every Y milliseconds, where Y is less than X. If the user requests to view a waveform of a signal traced during the re-emulation, the host system can retrieve the stored signal and display a plot of the signal (generates a waveform of the signal). Afterwards the user can, for example, request to re-emulate the same component but for a different time period or to re-emulate another component.

A host system typically comprises at least seven sub-systems: a design synthesizer, a mapping module, a run time module, a results module, a debug module, a waveform module, and a storage module. Each of these sub-systems may be embodied as hardware, software, firmware, or a combination thereof. Together these components configure the emulator, and monitor the emulation results.

The design synthesizer converts the HDL of a DUT into gate level logic. For a DUT that is to be emulated, the design synthesizer receives a description of the DUT. If the description of the DUT is fully or partially in HDL (e.g., RTL or other level of abstraction), the design synthesizer 3210 synthesizes the HDL of the DUT to create a gate-level netlist with a description of the DUT in terms of gate level logic.

The mapping module partitions DUTs and maps partitions to emulator FPGAs. The mapping module partitions a DUT at the gate level into a number of partitions using the netlist of the DUT. For each partition, the mapping module retrieves a gate level description of the trace and injection logic and incorporates the logic into the partition. As described above, the trace and injection logic included in a partition is configured to trace signals exchanged via the interfaces of an FPGA to which the partition is mapped (trace interface signals). The trace and injection logic can be incorporated into the DUT prior to the partitioning. For example, the trace and injection logic may be incorporated by the design synthesizer prior to or after the synthesizing the HDL of the DUT. Hence, the trace and injection logic may not match the partitions, it may be a subset, a superset or even different from the partitions.

In addition to including the trace and injection logic, the mapping module may include additional tracing logic in a partition in order to trace the states of certain DUT components that are not traced by the trace and injection logic (to trace signals other than the interface signals traced by the trace and injection logic). The mapping module may include the additional tracing logic in the DUT prior to the partitioning or in partitions after the partitioning. The design synthesizer can include the additional tracing logic in an HDL description of the DUT prior to synthesizing the description.

The mapping module maps each partition of the DUT to an FPGA of the emulator. The mapping module performs the partitioning and mapping using design rules, design constraints (e.g., timing or logic constraints), and information about the emulator. For components of the DUT, the mapping module stores information in the storage module describing which FPGAs are to emulate each component.

Based on the partitioning and the mapping, the mapping module generates one or more bit files that describe the created partitions and the mapping of logic to each FPGA of the emulator. The bit files may include additional information, such as constraints of the DUT, and routing information of connections between FPGAs and connections within each FPGA. The mapping module can generate a bit file for each partition of the DUT, which can be stored in the storage module. Upon request from a user, the mapping module transmits the bit files to the emulator, which the emulator uses to configure the FPGAs to emulate the DUT.

If the emulator includes specialized ASICs that include the trace and injection logic, the mapping module may generate a specific configuration allowing to connect them to the DUT or just save the information of what traced/injected signal is and where the information is stored on the specialized ASIC.

The run time module controls emulations performed on the emulator. The run time module may cause the emulator to start or stop executing an emulation. Additionally, the run time module may provide input signals/data to the emulator. The input signals may be provided directly to the emulator through the connection or indirectly through other input signal devices. For example, the host system with the run time module may control an input signal device to provide the input signals to the emulator. The input signal device may be, for example, a test board (directly or through cables), signal generator, another emulator, or another host system.

The results module processes emulation results generated by the emulator. During emulation and/or after completing the emulation, the results module receives emulation results from the emulator generated during the emulation. The emulation results include signals traced during the emulation. Specifically, the emulation results include interface signals traced by the trace and injection logic emulated by each FPGA. The emulation results may also include signals traced by additional logic included in the DUT. Each traced signal can span multiple cycles of the emulation. A traced signal is comprised of multiple hardware states and each hardware state is associated with a time of the emulation. The results module stores the traced signals received in the storage module. For each stored signal, the results module can store information indicating which FPGA generated the traced signal.

The debug module allows users to debug DUT components. After the emulator has emulated a DUT and the results module has received the interface signals traced by the trace and injection logic during the emulation, a user may request to debug a component of the DUT by re-emulating the component for a specific time period. In a request to debug a component, the user identifies the component and indicates a time period of the emulation to debug. The user's request can also include a sampling rate that indicates how often hardware states should be saved by logic that traces signals.

The debug module identifies the one or more FPGAs of the emulator that are configured to emulate the component based on the information stored by the mapping module in the storage module. For each identified FPGA, the debug module retrieves, from the storage module, interface signals traced by the trace and injection logic of the FPGA during the time period indicated by the user (i.e., retrieve hardware states traced by the trace and injection logic that are associated with the time period).

The debug module transmits the retrieved interface signals to the emulator. The debug module instructs the debug module to run the identified FPGAs and for the trace and injection logic of each identified FPGA to inject its respective traced signals into logic of the FPGA in order to re-emulate the component for the requested time period. The debug module can also transmit the sampling rate provided by the user to the emulator so that the tracing logic traces hardware states at the proper intervals.

To debug the component, the emulator only has to run the FPGAs to which the component has been mapped. Additionally, the re-emulation of the component does not have to start from the beginning, but can start at any point desired by the user.

For an identified FPGA, the debug module can transmit instructions to the emulator to load multiple emulator FPGAs with the same configuration of the identified FPGA. The debug module additionally instructs the emulator to run the multiple FPGAs in parallel. Each FPGA from the multiple FPGAs is run with a different time window of the interface signals in order to generate a larger time window in a shorter amount of time. For example, for the identified FPGA to run a certain amount of cycles it may take an hour. However, if multiple FPGAs are loaded with the configuration of the identified FPGA and each of the FPGAs runs a subset of the cycles, it may only take a few minutes for the FPGAs to collectively run all of the cycles.

A user may identify a hierarchy or a list of DUT signals to re-emulate. To enable this, the debug module determines the FPGA needed to emulate the hierarchy or list of signals, retrieves the necessary interface signals and transmits the retrieved interface signals to the emulator for re-emulation. Hence, a user can identify any element (e.g., component or signal) of the DUT to debug/re-emulate.

The waveform module generates waveforms based on traced signals. If a user requests to view a waveform of a signal traced during an emulation run, the host system retrieves the signal from the storage module. The waveform module displays a plot of the signal to the user. For one or more signals, when the signals are received from the emulator, the waveform module can automatically generate the plots of the signals.

Detailed Description—Semantic Support

The signifier ‘commercial solution’ signifies, solely for the following paragraph, an engineering domain-specific (and thus non-preemptive—see Bilski) electronic structure, process for specified machines, manufacturable circuit (and their Church-Turing equivalents) or composition of matter that is useful in commerce to solve a problem of technology, that is, a use in commerce of an application of science or use in commerce of technology.

The signifier ‘abstract’ (when used in a patent claim for any embodiments disclosed herein for a new commercial solution that is a scientific application of one or more laws of nature {see Benson}, and that solves a problem of technology {see Diehr} used in commerce—or improves upon an existing commercial solution {see Diehr})—is precisely defined by the inventor(s) {see MPEP 2111.01} as follows:

a) a new commercial solution is ‘abstract’ if it is not novel (e.g., it is so well known in equal prior art {see Alice} and/or the use of equivalent prior art solutions is long prevalent {see Bilski} in science, engineering or commerce), and thus unpatentable under 35 U.S.C. 102, for example, because it is “difficult to understand” {see Merriam-Webster definition for ‘abstract’} how the commercial solution differs from equivalent prior art solutions; or

b) a new commercial solution is ‘abstract’ if it is obvious, that is, if the existing prior art includes at least one analogous prior art solution {see KSR}, or the existing prior art includes at least two prior art items that can be combined {see Alice} by a person having ordinary skill in the art {a “PHOSITA”, see MPEP 2141-2144} to be equivalent to the new commercial solution, and is thus unpatentable under 35 U.S.C. 103, for example, because it is “difficult to understand” how the new commercial solution differs from a PHOSITA-combination/-application of the existing prior art; or

c) a new commercial solution is ‘abstract’ if it is not disclosed with an enabling description either because there is insufficient guidance in the enabling description, or because only a generic implementation is described {see Mayo} with unspecified elements, parameters or functionality, so that a PHOSITA is unable to instantiate a useful embodiment of the new commercial solution, without, for example, requiring special programming {see Katz} or circuit design to be performed by the PHOSITA), and is thus unpatentable under 35 U.S.C. 112, for example, because it is “difficult to understand” how to use in commerce any embodiment of the new commercial solution.

Coverage Event Counting

Synthesis-based coverage collection implementation in emulation requires associating a counter with each coverage event. As described herein, there are different kinds of coverage that may be collected in emulation. Consider the following simple SystemVerilog covergroup as an example:

logic clk, a;

// clk and a getting their values somewhere

covergroup cg @(posedge clk);

cp: coverpoint a {bins b={1};}

endgroup:cg cg mycg=new;

Covergroup instance mycg is counting the number of cases when a has a value 1 on rising clock. The naïve synthesis of this coverage event would look like:

bit [31:0] ctr;

logic clk, a;

always @(posedge clk iff a) ctr++;

The foregoing example correlates a 32-bit counter ctr with this coverage event. This 32-bit counter is incremented each time a==1 on the rising clock.

32-bit counters impose heavy burden on emulation because the naïve implementation requires allocation of 32 flip flops for each counter, especially when millions of coverage counters are required to register all coverage events.

To cope with this problem, one can reduce the counter size (e.g., to eight bits), but then the counter may overflow. One of the possible ways of handling this situation would be to send once in every 2⁸=256 emulation cycles all counter values to the host and to reset all counters. This and similar solutions introduce communication performance overhead between the emulator and the host, and, even more importantly, these solutions introduce routing overhead, since it is required to provide routing from each counter to the output ports of the emulator.

Various embodiments reduce the capacity overhead introduced by coverage collection without introducing additional routing and performance overhead.

Smart Coverage Counter Implementation

Various embodiments implement coverage counters as Linear Feedback Shift Registers (LFSR). An n-bit LFSR is a shift register whose input bit is a linear function of its previous state, i.e., the new value of the register is computed as its current value shifted right by 1, with its most significant bit (MSB) is computed as a linear function L of the current state: new_value=current_value>>1|L(current_value)<<(n−1)

Alternative embodiments use left shift and the least significant bit instead. LFSRs may be implemented as a combination of shift registers and/or flip flops, and XOR-gates. Gates may be implemented in emulation as Look-Up Tables (LUT). It is always possible to construct for any n, an n-bit LFSR able to count up to 2^(n-m)−1.

For example, a 31-bit counter with a period of 2³¹, may be constructed as shown in FIG. 4. For its realization, two shift registers and one XOR gate (LUT) are utilized.

As another example, a 63-bit counter with a period of 2⁶³, may be constructed as shown in FIG. 5. For its realization, one 62-bit shift register, one flip flop and one XOR gate (LUT) are utilized. Other counter sizes may be implemented utilizing components for implementing a maximum-length LFSR configuration. Specific emulation hardware may have different primitives, but the number of the components remains small. Shift registers are usually available field-programmable gate array (FPGA) primitives.

Therefore, counter realization according to certain embodiments utilizes an approximately equivalent number of hardware resources regardless of the counting capability.

In certain embodiments, a counter value generated via a counter as discussed herein is encoded, and a decoding algorithm is utilized to extract the true value from the counters. To be usable, this algorithm must be fast, as a large amount of coverage counters needs to be decoded in the emulation runtime.

Counter Decoding

Certain embodiments are directed to the following method and implementation for converting an n-bit LFSR state, V, to an n-bit ordinal number representing the count of the detected events. Example values of n for practical needs are 31 or 63, however the decoding method is general, and is not limited to these values of n. In certain embodiments, the method comprises:

-   -   Pre-computing a static mapping table (an associative array) of a         subset of the LFSR bit patterns to corresponding ordinal         numbers, where the subset of bit patterns stored in the mapping         table is determined by a pre-chosen configuration of some m bits         in the n-bit vector of the LFSR bit pattern under consideration         to reduce the table size by 2^(m). Specifically, when said bit         vector has the most significant m bits equal to 0 (defining a         prescribed pattern), decoding overhead may be reduced, for it is         possible to allocate less space per table entry without need in         additional shift and masking operations, and to use one machine         instruction for comparison (although evident from the above         discussion, for explicit clarity, m is a value less than n);     -   per each value V to be converted: initializing the number of         iterations performed K to 0; while V does not match the pattern,         evaluating V=LFSR(V) and incrementing K (this iteration process         is stopped upon determining that V matches the prescribed         pattern);     -   consulting the mapping to retrieve the corresponding ordinal         number C;     -   returning C minus K as the result.     -   A method of the previous paragraph preceded by consulting a         pre-computed mapping table containing mappings from encoded bit         patterns V to corresponding ordinal numbers C for small values         of C, specifically for C<=10m, and optionally several other         precomputed mapping tables, of different values of m (e.g., m=8)         for ordinal numbers up to 2³², and with m=16, for ordinal         numbers up to 2³⁶.     -   Having several mapping tables for different ranges of ordinal         values speeds up coverage counters decoding because most of the         coverage events do not happen very often, and thus, their         counter values rarely exceed several millions of times per test.

The mapping table may have any of a variety of different implementations, e.g., as a hashed container, as a container accessed by binary search or as a search tree.

The following example with a 31-bit counter illustrates the above algorithm. To decode the binary number:

-   -   1011110101101111100010010010010

The method consecutively applies the counting function to the number until obtaining a number starting with nine binary zeros:

1. 0101111010110111110001001001001

2. 0010111101011011111000100100100

3. 0001011110101101111100010010010

4. 0000101111010110111110001001001

5. 0000010111101011011111000100100

6. 0000001011110101101111100010010

7. 0000000101111010110111110001001

8. 0000000010111101011011111000100

9. 0000000001011110101101111100010

For the last number, there is an entry for a value C in the map with the precomputed decoded value, say, 1011110101101111100010→C=981.

In the above example, 9 iterations (K) were necessary to get value 0000000001011110101101111100010, therefore, the decoded value of 1011110101101111100010010010010 is C−K=981−9=972. It should be understood that any number of iterations (K) may be required to generate a value having m most significant digits encompassing zero values. The number of iterations (K) is dictated by the counting function.

For sufficiently small sizes (e.g., not exceeding 32 bits), it is possible to construct a direct decoding map as an array, without storing the keys, since the keys—all encoded values with zero m MSBs, are just indices in this array. For example, for 31-bit counters such an array should have 2³¹⁻⁸=2²³=8M entries, each entry requiring 3 bytes, so that the memory overhead for this table is 24 MB.

For larger sizes, it is possible to set an overflow value: the fact that value V cannot be found in the decoding map(s) means that the corresponding ordinal number is greater than the maximal ordinal number present in the map(s) plus K. For example, for 63-bit counters one can tabulate 2³²⁻⁸=2²⁴ values, and if the decoded value cannot be found then this value is known to be greater than some number N, close to 2³², and the given value must be greater than N plus the number of iterations K required to get to the binary number having at least 8 leading zeros.

In the proposed method, the loop is completely devoid of memory access, unlike other decoding methods, as is illustrated in the sample of the Intel® 64 architecture assembly code below, and therefore is very fast:

movabsq $576460752303423487, %rcx

movq %rdi, %rax

cmpq %rcx, %rdi

jbe .L2

.p2align 4,,10

.p2align 3

.L4:

movq %rax, %rdx shrq %rdx xorq %rdx, %rax and1 $1, %eax salq $62, %rax

orq %rdx, %rax

cmpq %rcx, %rax

ja .L4

.L2:

Reading Coverage Counter Values

To avoid communication overhead, the counter values are read and sent to the host computer at the end of the emulation using a scan chain. This eliminates communication with a host during emulation, and introduces no routing overhead for sending counter values to the host.

When small counter sizes are used (e.g., 31 bits), they may overflow during one test emulation, and therefore, it is required to read them several times in the runtime. This entails stopping the emulation when the counters may overflow, reading all counter values via the scan chain and resuming the emulation. The corresponding performance penalty is small, typically 1-2 sec per hour.

CONCLUSION

The foregoing Detailed Description signifies in isolation the individual features, structures, functions, or characteristics described herein and any combination of two or more such features, structures, functions or characteristics, to the extent that such features, structures, functions or characteristics or combinations thereof are based on the present specification as a whole in light of the knowledge of a person skilled in the art, irrespective of whether such features, structures, functions or characteristics, or combinations thereof, solve any problems disclosed herein, and without limitation to the scope of the claims. When an embodiment of a claimed invention comprises a particular feature, structure, function or characteristic, it is within the knowledge of a person skilled in the art to use such feature, structure, function, or characteristic in connection with other embodiments whether or not explicitly described, for example, as a substitute for another feature, structure, function or characteristic.

In view of the foregoing Detailed Description it will be evident to a person skilled in the art that many variations may be made within the scope of innovations, embodiments and/or examples, such as function and arrangement of elements, described herein without departing from the principles described herein. One or more elements of an embodiment may be substituted for one or more elements in another embodiment, as will be apparent to those skilled in the art. The embodiments described herein were chosen and described to signify the principles of the invention and its useful application, thereby enabling others skilled in the art to understand how various embodiments and variations are suited to the particular uses signified.

The foregoing Detailed Description of innovations, embodiments, and/or examples of the claimed inventions has been provided for the purposes of illustration and description. It is not intended to be exhaustive nor to limit the claimed inventions to the precise forms described, but is to be accorded the widest scope consistent with the principles and features disclosed herein. Obviously, many variations will be recognized by a person skilled in this art. Without limitation, any and all equivalents described, signified or incorporated by reference in this patent application are specifically incorporated by reference into the description herein of the innovations, embodiments and/or examples. In addition, any and all variations described, signified or incorporated by reference herein with respect to any one embodiment are also to be considered taught with respect to all other embodiments. Any such variations include both currently known variations as well as future variations, for example any element used herein includes a future equivalent element that provides the same function, regardless of the structure of the future equivalent.

It is intended that the scope of the claimed inventions be defined and judged by the following claims and equivalents. The following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. Disclosed embodiments can be described with more features than are expressly recited in the claims. 

That which is claimed:
 1. A coverage event counter for hardware verification, the coverage event counter comprising: an n-bit linear feedback shift register (LFSR) for incrementing a counter upon detection of a coverage event; a decoder for correlating a bit pattern of the counter with numeric values, wherein the counter decoder is configured to: iterate the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value; correlate the (n−m) bit reduced value against one or more mapping tables to identify a numerical value; and decode the bit pattern counter based on the numerical value and the value K to generate a numerical counter value; an emulator using a scan chain to transmit the numerical counter value to a host computer, wherein the host computer is configured to receive the numerical counter value; and wherein n is a positive integer, m is a positive integer having a value less than n, and K is a positive integer.
 2. The coverage event counter of claim 1, wherein a mapping table of the one or more mapping tables is a static mapping table containing 2^(n−m)−1 or fewer values.
 3. The coverage event counter of claim 1, wherein the one or more mapping tables are each implemented as a hashed container.
 4. The coverage event counter of claim 1, wherein the consistent m-bit pattern portion is an m-bit string of binary zeros.
 5. The coverage event counter of claim 4, wherein the LFSR is a right-shift register, and wherein the m-bit string of binary zeros comprises the m most significant bits of the n-bit counter.
 6. The coverage event counter of claim 1, wherein decoding the bit pattern counter comprises subtracting K from the numerical value to generate the numerical counter value.
 7. The coverage event counter of claim 1, wherein the decoder is further configured to: detect an overflow condition based on the bit pattern of the counter; set the numerical counter value as a base numerical counter value; and loop through processes for: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value for an overflow portion; correlating the (n−m) bit reduced value for the overflow portion against one or more mapping tables to identify a numerical value; decoding the overflow portion of the bit pattern counter based on the numerical value and the value K to generate a numerical counter value for the overflow portion; and adding the numerical counter value for the overflow portion with the base numerical counter value to generate a complete numerical counter value.
 8. The coverage event counter of claim 1, wherein the coverage event counter is executable as a portion of a hardware verification emulator.
 9. The coverage event counter of claim 1, wherein the decoder is embodied as one of a hardware module or a software module.
 10. The coverage event counter of claim 1, wherein the one or more mapping tables comprises a plurality of mapping tables, wherein each of the plurality of mapping tables correlates to a different ordinal value range.
 11. The coverage event counter of claim 1, wherein the LFSR comprises a shift register, a flip flop, and an XOR gate.
 12. The coverage event counter of claim 1, wherein the n-bit LFSR is a 31-bit LFSR.
 13. The coverage event counter of claim 12, wherein K=8.
 14. The coverage event counter of claim 1, wherein the n-bit LFSR is a 63-bit LFSR.
 15. A method for counting coverage events for hardware verification, the method comprising: incrementing an n-bit counter of a linear feedback shift register (LFSR) for each detected coverage event; correlating a bit pattern of the counter with numeric values by: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value; correlating the (n−m) bit reduced value against one or more mapping tables to identify a numerical value; and decoding the bit pattern counter based on the numerical value and the value K to generate a numerical counter value; transmitting the numerical counter value to a host computer by an emulator using a scan chain, wherein the host computer is configured to receive the numerical counter value; and wherein n is a positive integer, m is a positive integer having a value less than n, and K is a positive integer.
 16. The method of claim 15, wherein one of the one or more mapping tables is a static mapping table containing 2^(n−m)−1 values.
 17. The method of claim 15, wherein the one or more mapping tables are each implemented as a hashed container.
 18. The method of claim 15, wherein the consistent m-bit pattern portion is an m-bit string of binary zeros.
 19. The method of claim 18, wherein the LFSR is a left-shift register, and wherein the m-bit string of binary zeros comprises the m most significant bits of the n-bit counter.
 20. The method of claim 15, wherein decoding the bit pattern counter comprises subtracting K from the numerical value to generate the numerical counter value.
 21. The method of claim 15, further comprising: detecting an overflow condition based on the bit pattern of the counter; setting the numerical counter value as a base numerical counter value; and looping through processes for: iterating the counter K iterations to generate an n-bit pattern having a consistent m-bit pattern portion and having an (n−m) bit reduced value for an overflow portion; correlating the (n−m) bit reduced value for the overflow portion against one or more mapping tables to identify a numerical value; decoding the overflow portion of the bit pattern counter based on the numerical value and the value K to generate a numerical counter value for the overflow portion; and estimating a complete numerical counter value of greater than K added with the numerical value identified from the one or more mapping tables.
 22. The method of claim 15, wherein the one or more mapping tables comprise a plurality of mapping tables, wherein each of the plurality of mapping tables correlates to a different ordinal value range.
 23. The method of claim 15, wherein the n-bit LFSR is a 31-bit LFSR.
 24. The method of claim 23, wherein K=8.
 25. The method of claim 15, wherein the n-bit LFSR is a 63-bit LFSR. 